---
title: R- Context Grabbing Assigning Metadata in Large Document Collections
enableToc: false
creation date: $=dv.current().file.ctime
last modified date: $=dv.current().file.mtime
author: 
year: 
reference: 
tags:
- resource
status: 
alias: "@hinrichsContextGrabbingAssigning2005"
---

- #references
    - Title: Context Grabbing: Assigning Metadata in Large Document Collections
    - Meta:
        - Tags: #ref/Paper
        - Authored by:: [[Joachim Hinrichs]] [[Volkmar Pipek]] [[Volker Wulf]] [[Hans Gellersen]] [[Kjeld Schmidt]] [[Michel Beaudouin-Lafon]] [[Wendy Mackay]] 
        - Year: [[2005]]
        - Publication: [[ECSCW]] 2005
        - URL: [Hinrichs et al. (2005). Context Grabbing: Assigning Metadata in Large Document Collections. ECSCW 2005](undefined)
        - URL: 
        - Citekey: hinrichsContextGrabbingAssigning2005
    - Content
        - Placeholder
        - Abstract
            - Classification schemes are an important issue in the collective use of large document collections. We have investigated the classification of technical documentations in two engineering domains: a steel mill and a sewerage plant company. In both cases we found a coexistence of different classification schemes and problems resulting from distributed local archives. In supporting human actors to maintain different classifications schemes while working on a common archive, we developed the concept of context grabbing. It allows assigning context information efficiently in the form of metadata. Based on a document management system, a tool kit for context grabbing was developed. Its evaluation in a sewerage service company allows us to comment on important aspects of understanding the role of classifications in collaborative work.
        - #context-snippets
            - ![](https://firebasestorage.googleapis.com/v0/b/firescript-577a2.appspot.com/o/imgs%2Fapp%2Fmegacoglab%2FYhHuwMz8Tp.png?alt=media&token=acf224fa-df96-4689-9ec0-abe2881f1cd9)
            - ![](https://firebasestorage.googleapis.com/v0/b/firescript-577a2.appspot.com/o/imgs%2Fapp%2Fmegacoglab%2FpX4rNj7Qga.png?alt=media&token=5919f57c-dac8-4bea-b75d-078a1629bd61)
                - pg 372
            - ![](https://firebasestorage.googleapis.com/v0/b/firescript-577a2.appspot.com/o/imgs%2Fapp%2Fmegacoglab%2FJ2Sqr7nsSy.png?alt=media&token=a5f60919-328e-43b9-8b79-d9043f2ba5d8)
            - ![](https://firebasestorage.googleapis.com/v0/b/firescript-577a2.appspot.com/o/imgs%2Fapp%2Fmegacoglab%2F7zrr6dqDHb.png?alt=media&token=b9d89e5a-f88c-473c-a7e3-04e6e0cac621)
    - #lit-context
        - [[ECSCW]] is where a lot of the [[m/Ethnography]] in context of **Work** is still alive (exited somewhat from [[CSCW]]), so we can have a bit more confidence that this is done well from a theoretical and methodological perspective
        - last author [[Wendy Mackay]] is super-prominent in [[CSCW]]
            - ex: chosen to summarize history of social comptuing research in the 1980's at the 2020 CSCW conference panel
    - #[[📝 lit-notes]]
        - useful precursor to idea of [[flexible compression]] as means for tackling [[C- Specifying context for future reuse is costly]]
    - #lit-context
    - #[[📝 lit-notes]]
        - **How did the authors approach their questions/problems?** ((most of this is going to come from the methods sections, although some info about conceptualization of key concepts might be relevant to pull from intro/lit-review)) #lit-context
        - **What did they find?** ((keep this as contextualized as possible; resist the urge to repeat claims or generalizations)) #[[observation-notes]]
            - Decentralized project documentation made recontextualization difficult for engineers because they didn't know the history of changes for a document or if a particular document was up to date, leading to issues such as "exploratory digging by hand" to avoid damaging power lines pg 375
                - [[P- Joel Chan]] comments
                    - this is looking pretty good in terms of granularity, i can work with this!
                    - would be nice to know more about what is meant by decentralized project documentation. 
                        - probably best to have a separate `observation note` block that summarizes that (with its own `context snippets`), and the block ref that into the "decentralized project documentation".